Service differentiation at an access point device

ABSTRACT

Adaptive pairing of an access point (AP) slice with other computing resource slices is disclosed. Pairing of an AP slice can comprise pairing to a radio access network (RAN) slice and/or to a network core component (core) slice. The pairing can be based on end point device information, AP environment information, user preference information, and state information for a RAN and/or CN slice. Coordinating or synchronization of AP, RAN, and/or core slices can enable streamlining of migration of a device from an AP component to a RAN component. Moreover, AP slice coordination can enable efficient use of network computing resources tailored to needs of devices connecting to an AP device. A determined pairing, e.g., AP-core, AP-RAN-core, RAN-core, etc., can be modified before provisioning or after provisioning in response to changes in device demands and/or AP state/environment.

TECHNICAL FIELD

The disclosed subject matter relates to slicing of access pointresources and, more particularly, to adaptively pairing of an accesspoint slice, a radio access network slice, and a core network slice, toenabling improved network resource allocation in comparison toconventional technologies.

BACKGROUND

Next-generation mobility networks including 5G cellular systems areanticipated to enable disruptive digital transformation in the societythat will enable people, machines, businesses, and governments withunprecedented capabilities to communicate and share informationeffectively. The demands on 5G can be high in terms of handling avariety of use cases associated with mobile-to-mobile and the ‘internetof things’ (M2M/IoT), augmented/virtual reality (AR/VR), telehealth,targeted mobile advertising, connected cars, etc. These new services canrequire a wide range of aggregate bit rates, low latencies, vehicularspeeds, device types and device capabilities, device densities, etc., toprovide consistent end user quality for a given service in heterogeneousenvironment. 5G network slicing can be used to allocate 5G resources toend devices.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of an example system that can facilitateadaptive pairing of an access point slice with a RAN slice and/ornetwork core slice, in accordance with aspects of the subjectdisclosure.

FIG. 2 is an illustration of an example system that can facilitateadaptive pairing of an access point slice with a RAN slice and/ornetwork core slice based on device information, in accordance withaspects of the subject disclosure.

FIG. 3 is an illustration of an example system that can enable adaptivepairing of an access point slice with a RAN slice and/or network coreslice based on a user preference and device information, in accordancewith aspects of the subject disclosure.

FIG. 4 illustrates an example system that can facilitate adaptivepairing of an access point slice with a RAN slice and/or network coreslice to facilitate migration of an end point device between an accesspoint device and a RAN device, in accordance with aspects of the subjectdisclosure.

FIG. 5 illustrates an example system that can facilitate adaptivepairing of an access point slice with a RAN slice and/or network coreslice based on device information and user preference informationretrieved from a data store, in accordance with aspects of the subjectdisclosure.

FIG. 6 is an illustration of an example method, enabling adaptivepairing of an access point slice with a RAN slice and/or network coreslice, in accordance with aspects of the subject disclosure.

FIG. 7 illustrates an example method, facilitating adaptive pairing ofan access point slice with a RAN slice and/or network core slice tosupport device handover, in accordance with aspects of the subjectdisclosure.

FIG. 8 illustrates an example method, enabling inferred adaptive pairingof an access point slice with a RAN slice and/or network core slice, inaccordance with aspects of the subject disclosure.

FIG. 9 depicts an example schematic block diagram of a computingenvironment with which the disclosed subject matter can interact.

FIG. 10 illustrates an example block diagram of a computing systemoperable to execute the disclosed systems and methods in accordance withan embodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

Coordinating radio access network (RAN) slices and network core (CN)slices has, to date, been highly beneficial in telecommunications.Extending slicing, and therefore further extending these benefits, canbe highly desirable. In this regard, as mentioned, 5G and other evolvingwireless network technologies can be highly resource intensive in termsof handling mobile-to-mobile, the ‘internet of things’ (M2M/IoT),augmented/virtual reality (AR/VR), telehealth, targeted mobileadvertising, connected cars, and other services/technologies. Theseservices/technologies can require a wide range of aggregate bit rates,low latencies, device types and device capabilities, device densities,etc., to provide consistent end user quality for a given service in aheterogeneous networking environment. Further, home and/or enterpriseaccess point (AP) wireless networks, such as provided by local wirelessAPs, micro-cells, nano-cells, pico-cells, etc., as compared to publicaccess cell-type wireless systems, can also demonstrate a lack offunctionality and adaptivity in providing granular services to end pointdevices based on service types, applications, security/privacy, etc. Asan example, data traffic typically does not support differentiatingbetween time-sensitive, mission critical services, and other services.Moreover, conventional AP data does not support interworking withcellular/wireless network slicing. As such, the more end point devicesconnecting to an AP network, generally the slower the average speed foreach end point device and adding more devices then bogs down otherdevices. Where it can be expected that increasingly more devices willrequire connectivity, e.g., as part of internet of things (IOT),proliferation of personal wireless devices, etc., to local APnetwork(s), it can be desirable to increase availability and scalabilityof AP network(s) and interoperability with RAN network(s).

Given that network architecture with a single set of standard mobilitynetwork functions can be extremely complex and expensive to deploy in amanner that can be able to meet the demanding performance requirementsfor a wide variety of mobility services, network slicing concepts canenable use of standardized network elements and functions in a mannerthat can be dynamically re-configurable within an AP network, a RANnetwork, core components of a network, etc. As such, a network operatorarchitecture can create and deliver a given mobility service via acoordinated slicing of various parts of the communications pathway,e.g., combinations of slices of one or more of an AP, RAN, core, etc.Logically slicing an AP, RAN, core, etc., network into multiple virtualnetworks can enable designation of and/or optimization of each slice tomeet dynamically changing resource needs, demands, expectations, etc.Given the scarce physical radio resources of an AP or RAN, and theirallocations and utilizations in space domains, frequency domains, andtime domains, it can be possible to define end-to-end network slicingwherein one or more network core (CN) slice is intelligently paired withone of more AP and/or RAN slice to adaptively define an end-to-endnetwork-on-demand for services employing differing application(s) and/orservice(s), business agreement(s), etc. Moreover, handover between an APand a RAN, and/or between APs and RANs, can be facilitated, e.g., an APslice and a RAN slice can be selected to facilitate movement of an endpoint device between an AP and a RAN, which can include moving from afirst AP to a first RAN, from a first RAN to a first AP, from a first APto a second AP, from a first RAN to a second RAN, etc.

Pairing or binding can adaptively couple a RAN slice(s), and AP(s)slice, a CN slice(s), or combinations thereof, to provide desired orindicated features, performance, cost, efficiency, etc. In contrast torandom pairing between slices, intelligent pairing can allocate aresource(s) in real time or near real time, and in a manner that canreflect business goals. Moreover, intelligent slice allocation canaccommodate updating of slices, substitution of slices, adding newslices, removing slices, or nearly any other adaptation of a combinationof slices being employed by an end point device. The disclosed subjectmatter can generally be discussed in terms of user equipment (UE) endpoint devices and the term UE can generally be used to indicate all endpoint devices for brevity. It is noted that the term UE can generally beregarded as being including of non-user equipments, such as some IOTdevices, etc., unless explicitly or implicitly contraindicated, e.g.,all end point devices can be referred to as UEs herein, unless it isclear from the context or written description that the term UE should bemore narrowly interpreted as specifically referring to a user ornon-user equipment. Moreover, end-to-end network slicing can be referredto as ‘network slicing’ and a network slice can comprise an AP slice(s),a RAN slice(s), a CN slice(s), or a combination thereof, and can bedistinct from CN slicing that does not consider a RAN slice, and asdistinct from RAN slicing that does not consider a CN slice. Further,the disclosed subject matter considers AP slicing in regard tocompatibility with RAN-CN slicing, e.g., the disclosed subject mattercan enable coordination of AP slicing to facilitate moving a UE to aRAN-CN slice pair, rather than just the RAN-CN pair in the absence of anAP slice. Similarly, the disclosed subject matter can enablecoordination of AP slicing to facilitate moving a UE from a RAN-CN slicepair to the AP slice, again rather than just considering the RAN-CN pairin the absence of the AP slice. In this regard, where RAN-CN slice pairsmay be known, the instant disclosure provides improvements by enablingcoordination with AP slicing.

Network slicing can transform a monolithic mobility networkingarchitecture that has traditionally been used to service smartphones inthe current wireless network provider industry. With the proliferationof new wireless technologies and next generation mobile devices, IOTdevices, etc., the connectivity and communication models previouslyemployed can be expected to rapidly evolve and drive the adoption of newservices which were not possible before. Moreover, as network functionstransform from physical to virtual domain, e.g., in a cloud centricenvironment, etc., this transformation can open up innovativeopportunities to be able to design fully programmable mobile networks,for example, network that can deliver a ‘micro-service architecture’,etc. Programmable or adaptive network technology concepts can be appliedto core networks and can extended to radio access networks and/or APnetworks, to provide radio resources and create a robust network slicingconcept that can work in a coordinated manner.

Within a single frequency band for an AP device, services can beapportioned to one or more slice(s) that can be selectable in terms oftheir utilization in space, time, frequency domain, etc. Each suchslice, and combinations of such slices, can be employed to providedifferent sets of services, e.g., based on UE requirements in areal-time or near real-time manner. Thus, dynamic spectrum managementcan enable spectral allocation via configurable slices of an AP, RAN,CN, etc., wherein slice combinations can provide adaptable services to aUE. Slicing can enable provision of applications/services of one or moredevices across one or more groups of devices with similar or identicalcharacteristics, for example, narrow band IoT devices that can operatein a 200 kHz channel for infrequent and short data transmission canemploy an AP slice that can be narrow and temporally multiplexed toserve the one or more IOT devices. The example IOT devices can bedevices such as, but not limited to, sensors, utility meters that canwake up to report their readings and then return to an extended sleepmode, parking meters that report upon use then return to a sleep mode,etc. Similarly, another example AP slice can provide greater bandwidthto other groups of UEs, e.g., computers, tablets, smartphones, videodoorbell systems, etc., that can be different from the slices allocatedfor the aforementioned example IOT devices.

Moreover, an example AP slice can be re-allocated, for example, as astandalone resource, etc., combined with other radio slices perappropriate rules for aggregation, etc., to satisfy changing serviceconditions/requirements, e.g., where the AP slice can be subsequentlyused to provide service to other devices including mobile broadbandsmartphones, more spectrum demanding classes of IoT devices, etc. Theexample AP slice allocation can adapt in real-time, or near real-time,and can maintain a record of historical AP slice allocation(s),pairing(s), etc., to facilitate future use by the example less demandingIoT devices as they are deployed, though subject to prompt adaptationbased on current spectral/performance demands. As such, analysis ofinformation pertaining to the device/service using the spectrum, inaddition to analysis of the AP slice and/or a RAN/CN slice, cantherefore enable intelligent use of historical information to facilitateallocation of an end-to-end network slice, which can then be adaptedbased on the demands/performance in the present use of the networkslice. In an embodiment, the analysis can be performed based on thehistorical information and current use prior to allocation of thenetwork slice, e.g., AP, RAN, CN slice combinations. In an embodiment,the historical information can be employed to select an initial networkslice that can then subsequently be adapted based on the current use.Adaptation of a network slice can comprise adaptation of an AP slice, aRAN slice, a CN slice, or combinations thereof. Moreover, the adaptationcan be used to update stored historical data. Adaptation of the AP slicecan include changes to the time, frequency, space, etc., of the APslice, merging AP slices, divesting AP slices, ranking AP slices,ordering AP slices, shifting an AP slice in frequency, time, space,etc., coordinated use with another AP slice, etc. Similarly, adaptationof a RAN slice and/or a CN slice can merge, divest, rank, order,coordinate use of, add/remove functionality to, etc., these otherslices, e.g., adding/removing one or more virtual network function (VNF)to a CN slice, etc. Adapting an AP slice can be performed in anautomated manner, e.g., in a software deployed network (SDN), vianetwork function virtualization (NFV), etc. As an example, intelligentselection of a slices can result in offloading non-critical traffic froma RAN slice to an AP slice, to a different RAN or CN slice, from a firstAP slice to another AP slice, etc. As an example, a priority of servicesin a given location, a subscriber agreement parameter, historical use bya device requesting access to a service, planned/unplanned maintenanceof an AP/RAN/CN device, changes in use of networking resources,availability of alternate VNFs, etc., can cause adaptation of an APslice or combination of an AP slice with a NC slice, RAN slice, etc. Assuch, the disclosed subject matter can support service differentiationand resource segmentation that can provide improved customersatisfaction, for example, via adaptive AP resource segmentation,granular service differentiation for UEs, contextual selection ofappropriate AP slice(s), enabling different tiers of security slicesand/or privacy slices, automating interworking of AP slices with RANand/or CN slices, for example, based on services, applications,indicated performance, historical use, etc.

To the accomplishment of the foregoing and related ends, the disclosedsubject matter, then, comprises one or more of the features hereinaftermore fully described. The following description and the annexed drawingsset forth in detail certain illustrative aspects of the subject matter.However, these aspects are indicative of but a few of the various waysin which the principles of the subject matter can be employed. Otheraspects, advantages, and novel features of the disclosed subject matterwill become apparent from the following detailed description whenconsidered in conjunction with the provided drawings.

FIG. 1 is an illustration of a system 100, which can facilitate adaptivepairing of an access point slice with a RAN slice and/or network coreslice, in accordance with aspects of the subject disclosure. System 100can comprise network core component (core) 110. Core 110 can becommunicatively coupled, via communication framework 190, to radioaccess network (RAN) 120, access point (AP) 130, etc. Communicationframework 190, for example, can comprise a backhaul connection betweenRAN 120 and core 110, a fiber optic connection between AP 130 and core110, etc. In modern systems, communication framework 190 can be expectedto comprise one or more modalities of communication technologies, e.g.,fiber optic, digital subscriber lines, copper wiring, over-the-airoptical connectivity, radio frequency connectivity, etc., and, as such,a connection between AP 130 and core 110 can traverse differentcommunication modalities that can be owned, operated, etc., by one ormore different entities, e.g., a phone line can connect AP 130 to alocal exchange where communication can be converted to optical signalssent on fiber to other devices that eventually route communications tocore 110. Similarly, communicating back to the example AP 130 cantraverse the same or different modalities.

An end point device, e.g., a UE, can be communicatively coupled to AP130 in example system 100. A UE can be laptop computer 102, smart phone104, or nearly any other user or non-user device, e.g., an IOT sensor, asurveillance camera, a printer server, a television, a media server, awireless audio device, a connected thermostat, a wireless smokedetector, tablet computer, laptop computer, video game console,sprinkler controller, lighting controller, smart doorbell, broadbandgateway component, etc. Each end point device can request and beallocated wireless connectivity via an AP component, e.g., AP 130, etc.In some embodiments, one or more AP 130 can provide service areacoverage jointly, for example, a residence can have multiple overlappingareas of wireless coverage provided by corresponding wireless nodes thatcan act as one or more AP 130. Accordingly, some apportionment ofavailable AP resources can occur. In conventional systems, apportionmentcan include evenly dividing AP resources among all requesting UEs. Thiscan result, for example, in a media server being provided withequivalent priority and resource access as a baby monitor, a humiditysensor on a deck weather station, and a smart doorbell even though eachof these UEs can have different network resource needs. Theindiscriminate sharing of AP resources can result in inadequatelyserving some UEs that can otherwise be associated with higher priority.As an example, the media server can burden AP resources by streamingmusic at high quality which can result in congestion that can causedelay for a smart doorbell that might cause an occupant of a house tomiss a notification that a package was just left at the door, exposingthe package to potential theft. In another example, a child playingonline video games and consuming a majority of shared bandwidth from anAP device can cause a parent's video conference to have latency issuesand degraded performance. Similarly, making all services available toall UEs all the time can be inefficient.

In system 100, AP 130 can comprise an AP slicing component that canprovide adaptable AP resource segmentation and granular servicedifferentiation between UEs. As such, the AP resources can be adaptivelydivided, for example to provide up to a fixed amount of AP resources. Asan example, a percentage of total available AP resources, e.g., wirelessbandwidth, can be apportioned to all IOT devices of a home, anotherpercentage to a parent's devices, another percentage to children'sdevices, and some portion to guests or passersby. Within these exampleAP resource partitions, services can be made available with granularity,for example, in the IOT portion, a first slice can provide low latencythat can be useful to end point devices such as smoke alarms, motionsensors, smart doorbell devices, etc., while a second slice in this sameportion can have access to higher latency services that can beacceptable for sensors like precipitation sensors connected to anirrigation system, light sensors of an automatic window blind controlsystem, etc. Similarly, in the example children's partition, slices canbe generated that focus on video gaming, streaming video/music, etc. Inthese examples, the AP partition of the parent can remain unaffected bythe use of other partitions, for example, the children streaming videocan be inconsequential to the parent's AP partition.

Further, the slicing of the AP resources can enable contextual selectionof an AP slice, slicing with different security tiers, slicing withdifferent privacy tiers, etc. In an example, an AP partition can be‘larger’, e.g., a greater percentage of total AP resources, during afirst time period and ‘smaller’ during another time period. In thisexample, the previously mentioned children's AP partition can be madelarger between 3 pm and 9 pm on weekdays to facilitate the kidsincreased use of AP resources for relaxation after school or to performschoolwork, etc. In another example, providing a slice of the children'sAP partition to a gaming system that was just activated can beassociated with providing a slice adapted for gaming based on detectinga type of device for the gaming system, e.g., when the device isidentified as a gaming system a gaming system slice can be provided fromthe children's partition. Similarly, detecting a UE is a baby monitor orsecurity camera, for example, can result in slicing the AP resourceswith heightened security services to better protect access to data onthat slice, e.g., more rigorous authentication services to access thedata of that slice can be implemented to, for example, prevent video ofthe inside of a user's home from being more easily accessible thanwithout the increased security of the slice.

In system 100, it can be appreciated that slicing at AP 130 can beaccomplished independent of slicing at RAN 120 or core 110. However, itcan be beneficial to coordinate AP 130 slices with RAN 120 and core 110slices. As an example, RAN 120 and core 110 can have slice pairs thatcan provide first services. In this example, AP 130 slicing that canemulate RAN 120 slicing can allow AP 130 and core 110 slice pairs thatcan be the same as, or similar to, the RAN 120 and core 110 slice pair.In this regard, UE 104 can readily transition between AP 130 and RAN 120with little to no change in the slice pair performance. Similarly, UE102 can transition form RAN 120 to AP 130 in a coordinated manner whereAP 130 and RAN 120 are performing coordinated slicing, more especiallyin coordination with core 110. As an example, a RAN 120 slice canprovide a slice with a first latency and a first bandwidth, wherein AP130 can provide a slice with a second latency and a second bandwidth. Inthis example, where the first and second latencies and bandwidth arevery different, there can be increased complexity in migrating a UEbetween AP 130 and RAN 120, in either direction. However, in thisexample, where the first and second latencies and bandwidths are similaror the same, then migration can be less complex. Further, in thisexample, where each of the first and second latencies and bandwidths ofthe slices of AP 130 and RAN 120 are both coupled to similar services inslices of core 110, this can reduce complexity of handing over a UEbetween the RAN and AP in comparison to the example AP slice beingcoupled to very different core slices than the RAN slices.

Generally speaking, a slice can be a virtualization of a physicalnetwork or component that can enable independent architecture,partitioning, and organization of computing resources within each slice.This can facilitate flexibility that is typically not readily availablein a monolithic embodiment of interconnected physical networkcomponents. A physical AP can be sliced into virtual AP slices such thatthe one or more virtual AP slices can each be adapted according tocorresponding characteristics, e.g., adapted to perform a specific typeof communication or service better than a generic channel of amonolithic physical AP device. Similarly, a CN slice can also be avirtualization of a physical CN resource, and a RAN slice can be avirtualization of a physical RAN resource. Typically, a slice, e.g., anAP, RAN, or CN slice, can be considered self-contained with regard tooperation, traffic flow, performance, etc., can have its own virtualizedarchitecture and features, and can be individually provisioned in anetwork. The virtualization of physical network resources via slicingcan simplify creation, management, and operation of slices, typicallytailored to a type of functionality, environment, service, hardware,etc., to enable efficient consumption of network resources of thephysical network. As examples, a first slice can have a first bandwidthand a second slice can have a different second bandwidth; a first slicecan have a different latency than a second slice; a first slice canemploy different virtual functions, e.g., VNFs, than a second slice,etc. As disclosed herein, selection of an AP, RAN slice, CN slice, orcombinations thereof, can provide benefit to a network by efficientlyemploying the corresponding resources of the end-to-end network, suchas, in a end-to-end network where an AP is wirelessly connected to a RANthat is connected to a core via a backhaul link, by pairing a narrowspectral AP slice, with a narrow spectral RAN slice, and with a CN slicethat supports IoT devices via VNFs frequently employed by an IoT device,which can be more efficient than pairing a wide spectral RAN slice withthe same AP and CN slices that can result in wasting the extra spectrumallocated via the wide spectral RAN slice. Other more nuanced examplesare readily appreciated and considered within the scope of the presentlydisclosed subject matter even where not explicitly recited. As such,slicing can be based on aspects, characteristics, features, bandwidth,jitter, frequency, or nearly any other aspect of AP component 130,including those not explicitly recited here for the sake of clarity andbrevity. Similarly, RAN and/or CN slicing can relate to aspects,characteristics, features, virtualized functions, e.g., VNFs, or nearlyany other aspect of RAN component 120 and/or CN component 110, includingthose not explicitly recited here for the sake of clarity and brevity.

UE information, e.g., device information 206, 306, 506, etc.,corresponding to UE 104 UE 102, etc., can comprise informationpertaining to a device that is expected to use, or is requestingprovisioning of, an AP, RAN, CN, or combined network slice. Deviceinformation can comprise a device identifier, device historyinformation, an indication of device type/functionality, an indicationof device radio parameters, a subscriber identifier associated with thedevice, an indication of what version of software is available on thedevice, etc. In an aspect, the device information can be employed toidentify a device, user, subscriber, service, functionality, etc. Inanother aspect, the device information can also directly or indirectlyindicate parameters for an AP, RAN, CN, or combined network slice. Thedevice information can further comprise information for devices otherthan the device itself, for example, device information can be employedto access historical use information stored on a remotely locatedstorage device, e.g., data store 592, etc., access subscriber contractparameters, e.g., via a network subscriber information component of CN110, etc., or other corresponding information that can be employed inselecting an AP, RAN, CN, or combined network slice. As a rudimentaryexample, a ‘connected thermostat’ can report data that is comparativelysmaller than might be associated with data from a tablet computer in useand, as such, can typically employ a narrower bandwidth connection thanthe example tablet computer. Accordingly, the example connectedthermostat can be directed to a narrow AP slice of AP component 130.Moreover, the example thermostat can employ different core networkfunctionality than the example tablet computer, e.g., the tablet mightuse a billing function in relation to streaming data while the examplethermostat might have no need of such core network functionality.Accordingly, the example connected thermostat can be directed to a CNslice having functionality, e.g., VNFs, that are better tailored to thereporting of small bursts of intermittent data and that can avoidallocation of a CN slice that houses other extraneous VNFs, such as amobile billing VNF. This AP-CN slice pair can be correlated with theidentity of the example connected thermostat, with the type of device ofthe example connected thermostat, etc., such that where the device laterrequests a connection via the network of the network provider, theidentity of the device can be used to access the previously allocatednetwork slice, e.g., the AP-CN slice pair previously used, to affordrapid provisioning of the network slice. Similarly, where an examplesecond connected thermostat requests a connection, device information ofthe second thermostat can comprise the device type, which, where it isthe same/similar type as the first example connected thermostat, thedevice type information can be used to pair the same network slice forthe second example connected thermostat as was previously used by thefirst example connected thermostat, even where the second thermostat isin another household with a different AP component than AP component130, e.g., the first household can be used to facilitate provisioning ina second unrelated household based on the device type and historicalslicing. In similar examples, a UE can be a smartphone that can connectvia an AP-CN slice pair that can be used to generate a RAN-CN slice pairto accommodate handover of the smartphone from AP 130 to RAN 120 withbetter service coordination than without the AP-CN slice pairinformation.

In embodiments, alternative AP, RAN, CN, or combinations of slices canbe available that may rank higher than a slice based solely on deviceinformation. As an example, a newer VNF can be available on a differentCN slice than was previously used by the aforementioned exampleconnected thermostat, such that this new VNF slice can be selected overthe previously employed slice pair where the newer VNF is more highlyranked according to a corresponding metric. Accordingly, in someembodiments, potential slices can be sorted, ordered, ranked, selected,etc., to facilitate employing a preferred slice or slice combination. Asan example, a frequency of use, a performance measurement, a usersatisfaction indication, etc., can be used to increase/decrease aranking of an AP, RAN, CN, or combined slice. Rankings, ordering, etc.,of slices can evolve over time. In an example, a previously used networkslice can be highly ranked, however, where the AP slice informationindicates that the AP slice is no longer available, an alternate APslice can be increased in rank above the previously used AP slice of thepreviously used network slice. Continuing this example, where the CNslice information indicates that the CN slice is highly burdened byother devices, the CN slice ranking can be decremented, which may resultin selection of the same network slice despite decrementing the rankingof the CN slice portion or can result in selection of an alternative CNslice to pair with the new AP slice replacing the previously used APslice.

Provisioning of AP slices can be determined and initiated, in someembodiments, by AP component 130, e.g., AP component 130 can beindependently capable of provisioning an AP slice. In other embodiments,AP component 130 can provision slices responsively, e.g., slicingdetermination can be made remote from AP component 130, communicated toAP component 130, and AP 130 can responsively provision the indicated APslice. As an example, an AP router table can be updated based oninformation from core 110. In another example, RAN component 120 cancommunicate RAN slicing information to core 110 that can thencommunicate the RAN slicing information to AP component 130 to enable APcomponent 130 to emulate RAN slices of RAN component 120. Numerous otherexamples are readily appreciated and are all within the scope of theinstant disclosure even where not explicitly recited for the sake ofclarity and brevity.

In some embodiments, an inference can be formed by a machine learningcomponent, an artificial intelligence component, etc., which inferencecan be employed in determining, designating, sorting, ordering, ranking,etc., an AP, RAN, CN, or combination slice. The machine learningcomponent, the artificial intelligence component, etc., can be generallyreferred to as an inference component. The inference component cangenerate an expected result based on models, patterns, historical data,etc. As an example, an inference can be generated by an inferencecomponent of AP component 130 that can indicate that adapting a firstslice into a second slice at 6 pm can facilitate improved AP component130 performance based on historical use patterns, devices currentlyconnected to AP component 130, etc. However, an alternative inferencecan be determined that a most recently used AP slice is most preferredbased on other information. Either of these inferences, or otherinferences, can be determined based on machine learning, artificialintelligence systems, programming, rules, etc. As such, slice selection,ranking, ordering, sorting, etc., can be based on inferences of aninference component. In some embodiments, an inference component can belocated remotely from AP component 130.

FIG. 2 is an illustration of a system 200, which can enable adaptivepairing of an access point slice with a RAN slice and/or network coreslice based on device information, in accordance with aspects of thesubject disclosure. System 200 can comprise core 210 that can enablepairing of an AP slice with RAN and/or core slices. Core 210 cancomprise network slicing component (NSC) 212. NSC 212 can supportslicing of core computing resources, e.g., virtualizing core functionsand resources specific to identified criteria. As an example, a coreslice can comprise one or more of a group of VNFs made available via aportion of network resources that can be different than other possiblecore slices, which can allow access to those VNFs in a more efficientmanner than without slicing. NSC 212 can provide a slice that can beprovisioned via core 210 in a manner that can be combined with an APslice.

An AP slice can be determined by AP slicing component (APSC) 232 thatcan be comprised in AP component 230. An AP slice can virtualize APcomponent functions and resources specific to identified criteria in amanner similar to slicing of core computing resources. APSC 232 canslice AP computing resources based on information from an end pointdevice (device info) 206. In some embodiments, APSC 232 can receive coreslicing information, e.g., via communication framework 290, etc., andcan determine an AP slice further based on the received core sliceinformation. In some embodiments, APSC 232 can communicate AP sliceinformation to NSC 212, e.g., via communication framework 290, etc., tofacilitate NSC 212 determining core slices based on AP slices, whereindetermining a slice can comprise identifying slice parameters,generating a slice, selecting a slice, causing a slice, etc.

As such, an AP slice and a core slice can be coordinated to facilitateefficient interoperation. As an example, an AP slice can be determinedthat can implement a VNF that is comprised in a core slice. As anotherexample, a core slice can implement a VNF employed in an AP slice. Inthese examples, use of a matching VNF can be more efficient thatemploying an AP slice and a core slice that use different VNFs. Deviceinfo 206 can comprise indicators of a UE type, a requested computingresource and/or VNF, a requested quality of service (QoS), a requestedlatency value, a requested throughput value, etc. As such, AP 230, viaAPSC 232, can generate an AP slice that can be tailored to a UEcomputing resources request. As an example, a first AP slice can begenerated for a UE that is an IOT type device that can be associatedwith a low volume of data throughput and comparatively higher acceptablelatency than for a second AP slice that can be requested by a UE thatcan be a personal computer (PC) belonging to an account owner that canrequest a lower latency threshold and greater amount of bandwidth.

Moreover, an example AP slice can be coordinated with a core slice toprovide similar levels of allocated computing resources andfunctionality. In the preceding example, the AP slice for the IOT typedevice can be paired with a core slice having slower communicationslinks than another core slice that can be paired with the example secondAP slice for the account holders PC. It can be appreciated that pairingthe AP slice for the PC with a core slice relating to IOT devices can beless optimal than pairing the AP slice for the PC with a faster coreslice. In system 200, APSC 232 is illustrated as being comprised in AP230. However, in some embodiments, APSC 232 can be external to AP 230,e.g., comprised in another component on the AP 230 side ofcommunications framework 290. In some embodiments, APSC 232 can belocated on core 210 side of communications framework, or even in core210, e.g., AP 230 can communicate, via communication framework 290, datato enable a remotely located APSC 232 to determine an AP slice and tocommunicate data to implement the determined AP slice back to AP 230where the AP slice can be provisioned. However, in most implementationsof example system 200, AP 230 comprising APSC 232 can enabledistributed, rather than centralized, AP slice determination in a mannerthan can be more favorable than a centralized determination, e.g., manyAP components that can utilize a local APSC 232 can distribute thecomputing resource cost of determining and provisioning corresponding APslices at the many AP components in a manner that can be more efficientthan communicating data across communication framework 290 to enablecentralized AP slice determinations that are then sent back to the manyAP components.

FIG. 3 is an illustration of a system 300, which can facilitate adaptivepairing of an access point slice with a RAN slice and/or network coreslice based on a user preference and device information, in accordancewith aspects of the subject disclosure. System 300 can comprise core 310that can enable pairing of an AP slice with RAN and/or core slices. Core310 can comprise NSC 312. NSC 312 can support slicing of core computingresources to make one or more of a group of VNFs available via a portionof network resources that can be different than other possible coreslices. This can allow access to those VNFs in a more efficient mannerthan without core slicing. NSC 312 can provide a slice that can beprovisioned via core 310 in a manner that can be combined with an APslice.

System 300 can further comprise radio access network RAN component 320that can enable pairing of an AP slice with RAN and/or core slices. RANcomponent 320 can comprise RAN slicing component (RSC) 322. RSC 322 cansupport slicing of RAN computing resources to make one or more of agroup of VNFs available via a portion of network resources that can bedifferent than other possible RAN slices. This can allow access to thoseVNFs in a more efficient manner than without RAN slicing, similar tocore slicing. RSC 322 can provide a slice that can be provisioned viaRAN component 320 in a manner that can be combined with an AP slice.Moreover, RAN component 320 can determine a RAN slice in a manner thatcan be coordinated with core slicing, e.g., core slicing information canbe utilized in determining a RAN slice, RAN slicing information can beused to determine a core slice, etc. In this regard, RAN and core slicescan be coordinated. Moreover, coordination of RAN and/or core slices canbe similarly coordinated with an AP slice, e.g., a RAN/core slice can beutilized in determining an AP slice, an AP slice can be utilized indetermining a RAN/core slice, etc. An end result can be that an APslice, a RAN slice, and/or a core slice can be determined in acoordinated manner. In embodiments, this can enable efficient migrationof a UE between RAN 320 and AP 330. As an example, an IOT-type slice forAP 330 can facilitate determining, and pairing to, an IOT-type coreslice, which information can be communicated, e.g., via communicationframework 390, to RAN component 320 to facilitate determining anIOT-type RAN slice, such that, when an IOT migrates from AP 330 to RANcomponent 320, a similar slice can be available at RAN component 320that is inherently well matched to the existing IOT-type core slicealready in use.

An AP slice can be determined by APSC 332 that can be comprised in APcomponent 330. An AP slice can, as previously noted, virtualize APcomponent functions and resources specific to identified criteria in amanner similar to slicing of core computing resources. APSC 332 canslice AP computing resources based on device info 306. In someembodiments, APSC 332 can receive RAN slicing and/or core slicinginformation, e.g., via communication framework 390, etc., and candetermine an AP slice further based on the received RAN/core sliceinformation. In some embodiments, APSC 332 can communicate AP sliceinformation to RSC 322 and/or NSC 312, e.g., via communication framework390, etc., to facilitate RSC 322 and/or NSC 312 determiningcorresponding RAN/core slices based on AP slices. As such, an AP slice,a RAN slice, and/or a core slice can be coordinated to facilitateefficient interoperation.

An AP slice can be coordinated with a RAN/core slice to provide similarlevels of allocated computing resources and functionality. Inembodiments, APSC 332 can be comprised in AP 330. However, in someembodiments, APSC 332 can be external to AP 330, or even comprised incore computing resources, e.g., at core 310, etc. Moreover, in someembodiments, APSC 332 can be comprised in a RAN-side component, e.g.,RAN component 320, etc. In some embodiments, RSC 322 APSC 332 and NSC312 can be comprised in a core-side component, e.g., core 310, etc.,although this highly centralized slicing, in some embodiments, can beless efficient that distributing slicing components among RAN and/or APcomponents that can access distributed processors, memory, networkconnections, etc.

In embodiments, AP 330 can comprise user preference component 350 tofacilitate implementing AP slicing based on user preference information.User preference information can augment or supplant other informationrelevant to AP slicing, e.g., device info 306. As an example, userpreference information can indicate that an identified device, such as asecurity camera be allocated an AP slice that has moderate latency inlieu of a lower latency AP slice that might be selected based on deviceinfo 306 where, for example, a user is employing the security camera tomonitor the growth of a plant instead of monitoring a doorway, etc.,e.g., the need for the example security camera to promptly communicatevideo content can be lower than would typically be expected of asecurity camera where it is merely being used to see when a plant mightbe blooming instead of monitoring for an intrusion into a home. Inanother example, a user can indicate a preference to employ an AP slicewith grater bandwidth for a child's device during homework hours, whichcan be used in conjunction with device info 306 for the child's deviceconnecting to AP 330 to increase the bandwidth of an allocated AP slicethan at other times of day.

FIG. 4 is an illustration of a system 400, which can enable adaptivepairing of an access point slice with a RAN slice and/or network coreslice to facilitate migration of an end point device between an accesspoint device and a RAN device, in accordance with aspects of the subjectdisclosure. System 400 can comprise core 410 that can comprise NSC 412to determine core slices. Core 410 can coordinate core slicing withslicing determinations at RAN 420 and AP 430, as disclosed elsewhereherein, via communication framework 490, etc.

In embodiments, UE 404 can migrate between RAN 420 and AP 430. As anexample, UE 404 can be a user phone attached to RAN 420, e.g., a RANand/or core slice can be supporting the phone as the user approachestheir office on a morning drive into work. In this example, the user'sworkplace can comprise AP 430. Device info, e.g., device info 206, 306,etc., can comprise location data for the example user phone, such thatwhen the phone is determined to be approaching the workplace, AP 430 canbe signaled to determine an appropriate AP slice that, for example, canbe premised on a RAN and/or core slice associated with the phone on theexample drive into work. AP 430, in response to device info, signaling,etc., can determine a coordinated AP slice, such that when the phone isin range of AP 430, the phone can be handed over from RAN 420 to AP 430according to the coordinated AP slice. In this example, the determinedAP slice can provide similar parameters as the RAN slice and can furtherbe coordinated with the existing core slice. Similarly, where UE 4040migrates from AP 430 to RAN 420, coordinated slicing can be accomplishedto again provide efficient transition between an AP slice and a RANslice that can offer similar performance to the AP slice, and cangenerally be coordinated with a core slice that can be part of apreviously coordinated AP-core slice pair, e.g., a RAN-core slice paircan be selected that can be coordinated with an AP-core slice pair toenable efficient migration of UE 404 from AP 430 to RAN 420.

FIG. 5 is an illustration of a system 500, which can support adaptivepairing of an access point slice with a RAN slice and/or network coreslice based on device information and user preference informationretrieved from a data store, in accordance with aspects of the subjectdisclosure. System 500 can comprise core 510 that can enable pairing ofan AP slice with RAN and/or core slices. Core 510 can comprise NSC 512.NSC 512 can support slicing of core computing resources to make one ormore of a group of VNFs available via a portion of network resourcesthat can be different than other possible core slices. This can allowaccess to those VNFs in a more efficient manner than without coreslicing. NSC 512 can provide a slice that can be provisioned via core510 in a manner that can be combined with an AP slice.

System 500 can further comprise radio access network RAN component 520that can enable pairing of an AP slice with RAN and/or core slices. RANcomponent 520 can comprise RSC 522. RSC 522 can support slicing of RANcomputing resources to make one or more of a group of VNFs available viaa portion of network resources that can be different than other possibleRAN slices. RSC 522 can provide a RAN slice that can be provisioned viaRAN component 520 in a manner that can be combined with an AP slice.Moreover, RAN component 520 can determine a RAN slice in a manner thatcan be coordinated with core slicing, e.g., core slicing information canbe utilized in determining a RAN slice, RAN slicing information can beused to determine a core slice, etc. In this regard, RAN and core slicescan be coordinated. Moreover, coordination of RAN and/or core slices canbe similarly coordinated with an AP slice, e.g., a RAN/core slice can beutilized in determining an AP slice, an AP slice can be utilized indetermining a RAN/core slice, etc. An end result can be that an APslice, a RAN slice, and/or a core slice can be determined in acoordinated manner. In embodiments, this can enable efficient migrationof a UE between RAN 520 and AP 530.

An AP slice can be determined by APSC 532 that can be comprised in APcomponent 530. An AP slice can virtualize AP component functions andresources specific to identified criteria in a manner similar to slicingof core computing resources. APSC 532 can slice AP computing resourcesbased on device info 506. In some embodiments, APSC 532 can receive RANslicing and/or core slicing information, e.g., via communicationframework 590, etc., and can determine an AP slice further based on thereceived RAN/core slice information. In some embodiments, APSC 532 cancommunicate AP slice information to RSC 522 and/or NSC 512, e.g., viacommunication framework 590, etc., to facilitate RSC 522 and/or NSC 512determining corresponding RAN/core slices based on AP slices. As such,an AP slice, a RAN slice, and/or a core slice can be coordinated tofacilitate efficient interoperation.

In embodiments, AP 530 can comprise user preference component 550 tofacilitate implementing AP slicing based on user preference information.User preference information can augment or supplant other informationrelevant to AP slicing, e.g., device info 506. In embodiments, userpreference info 508 can be received by AP 530 and employed indetermining an AP slice. User preference info 508 can be employed toaugment or supplant AP slicing determinations based on device info 506,as previously noted elsewhere herein. In an embodiment, user preferenceinfo 508 can be stored via remotely located data store(s) 592. Datastore(s) 592, for example, can be embodied in a user profile that canreside on nearly any component of system 500, e.g., on core 520 oranother core component, at RAN component 520, at AP 530, in a remoteprofile server, etc. In some unillustrated embodiments, device info 506can similarly be stored remote from AP 530, for example, device info 506can be stored on a personal service of a user that can be attached to AP530 or some other AP component, can be stored on a core networkcomponent servicer, etc. In embodiments, data store(s) 592 can thereforefacilitate generation of more consistent AP slices at different APcomponents, for example, user preference info 508 can be stored at aremote server and can be communicated to a first AP component at auser's home and a second AP component at a user's office such that thehome and office AP components can determine corresponding AP slices thatcan both be premised on the user's preference data from the data store.

Moreover, in embodiments, AP slices can be adapted, updated, replaced,added, removed, etc., in more synchronized manner via storing of userpreference info 508, device info 506, etc. In an example, a user canupdate network interface card of a laptop computer while at the user'soffice, which can result in updating of an office AP slice based on theupdated network interface card. In this example, the updated AP sliceinformation can be employed to trigger updating of device info 506and/or user preference info 508 at data store(s) 592, such that when theuser returns home with the upgraded laptop computer, the user's home APdevice can implement a home AP slice reflective of the upgraded networkinterface card, e.g., identifying the user's laptop is connecting viathe home AP device can retrieve updated device info 506 and userpreference info 508 from data store(s) 592 to provide an appropriate APslice at home. Similarly, changes to user preference info 508 at theexample user's home can be automatically propagated to the office APdevice via data stored(s) 592. In this regard, the centralization ofdevice libraries, reference libraries, etc., can further propagate toRAN slices and/or core slices where RAN/core slices can be coordinatedwith AP slices. As an example, the upgraded network interface card ofthe previous example laptop can result in adapting an AP slice, whichadaptation can result in adapting a core slice. This adapted core slicecan then cause determining of a different RAN slice than may havepreviously been employed, e.g., when the user came into work before thenetwork interface card upgrade a first RAN slice can be paired with afirst core slice that can be coordinated with a first AP slice when theuser arrives at the office, then, after the upgrade to the laptop, thefirst AP slice can be adapted to a second AP slice, which can result inadapting the first core slice to a second core slice, such that when theuser leaves the office, a second RAN slice can be determined based onthe second AP slice and/or second core slice. In this example, thesecond RAN slice can then facilitate handover to a third AP slice at theuser's home, wherein the third AP slice can be based on the second RANslice and/or the second core slice. In some embodiments, device info 506can be updated, such as via data store(s) 592, to enable updating theexample third AP slice based on the updated device info, or even on thesecond AP slice from the office. This end-to-end coordination can beparticularly valuable where AP, RAN, and/or core slicing is updatedoften, e.g., where pairings of AP, RAN, and core slices are regularlyupdated, propagating these changes to subsequent slices to facilitatecoordination can result in better synchronization of slices.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 6 -FIG. 8 .For purposes of simplicity of explanation, example methods disclosedherein are presented and described as a series of acts; however, it isto be understood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 6 is an illustration of an example method 600, which can facilitateadaptive pairing of an access point slice with a RAN slice and/ornetwork core slice, in accordance with aspects of the subjectdisclosure. At 610, method 600 can comprise determining an access point(AP) slice based on device information of a device requesting connectionto an AP component. AP slicing can provide adaptable AP resourcesegmentation and granular service differentiation between devicesconnecting to an AP, e.g., user equipment and/or non-user equipment,collectively generally referred to as UEs herein. A UE can requestperformance parameters of a connection to an AP device. Theseperformance parameters, e.g., bandwidth, QoS, throughput, latency,services, virtual network functions (VNFs), etc., can be reflected in aslice of AP device computing resources, e.g., one or more AP slices. Theslices can be determined therefore be based on device information, e.g.,device type, device model, device ownership, device performance metrics(key performance indicators (KPIs), etc.), user preferencescorresponding to the device and/or device environment, services to beimplemented via the device, or any of many other pieces of devicerelated information. As an example, a first AP slice can be differentthan a second AP slice based on what UE is requesting connection to theAP, when the device is connecting, what preferences are specified forthe connection, current AP device available resources, available VNFsand/or services, contracted service tiers, privacy designators, securityfeatures to be implemented, etc., e.g., an AP slice can be tightlydetermined to provide preferred levels of service to a connectingdevice. In some embodiments, the AP slice can be further based oninformation about available RAN and/or core network slices, e.g., tofoster coordination between one AP and RAN/core slices as has beendisclosed elsewhere herein.

At 620, method 600 can comprise coordinating the AP slice with a networkcore component (CORE) slice. Information about the AP slice can becommunicated to a network core component to facilitate coordination ofan AP slice and one or more core slice, one or more RAN slice, orcombinations thereof, as has been disclosed herein. It is noted that anAP slice that is not coordinated with a core slice can be morecomplicated to manage than an AP slice that is coordinated with a coreslice, e.g., a core slice and an AP slice that meet the same requestedperformance parameters can be more streamlined than moving data betweenan AP slice meeting designated parameters and one or more core slicesthat have different parameters. As an example, an AP slice can beselected to provide very low latency, for example to service anaugmented reality experience that suffers if there is data lag due tolatency. Pairing the example AP slice with a coordinated core slice cantherefore maintain the low latency performance requested for theaugmented reality application. However, if instead, the example AP sliceis pairs with a high latency core slice due to lack of coordination, theperformance of the augmented reality application can suffer. Inembodiments, information corresponding to the AP slice can becommunicated to a network core component that can attempt to provideaccess to, or determine, a coordinated core slice. In some embodiments,core slice information can be propagated to the AP device to facilitatecoordinated determination of an AP at 610, e.g., the determination ofthe AP slice can be based on predetermined core slice information. Insome embodiments, information about potential core slicing can becommunicated to the AP device, the AP device can determine the AP sliceat 610 in the context of the potential core slicing to enable thecoordination at 620 to already be possible, e.g., the AP device can beaware of the extents of core slicing so that the AP slice is within theextents and a coordinated core slice can be readily deployed. This canavoid conditions where the AP slice has performance parameters that arenot supported by any possible core slice(s), for example, a core slicemay have a predefined group of VNFs that can be limiting to some APslices, etc.

Method 600, at 630, can comprise, in response to determining a change indevice usage, updating the AP slice and the coordination with the coreslice. At this point, method 600 can end. At 630, method 600 candescribe adapting an AP slice and the corresponding core slice. Wherethe demand s on the AP computing resources, e.g., processors, memory,network, etc., change, for example due to a change in use or function ofa UE, the AP slice can be adapted. In this regard, adapting the APslice, and also the core slice, can comprise updating the sliceparameters, VNFs, services, etc., adding a slice, deleting a slice,merging slices, dividing a slice(s), determining a new slice, etc. As anexample, a UE streaming music can be allocated an AP slice, coordinatedwith a core slice, that has moderate latency, minimal throughput, and adata caching VNF to buffer against network interference/interruptions.Where the example UE opens a real-time video conferencing application,the AP, for example, can add an additional AP slice to support the videoconference with a low-latency and high bandwidth slice that can bepaired with an adaptation to the latency and bandwidth parameters of thecore slice, e.g., the AP slice can be modified by adding an additionalAP slice while the core slice can have slice parameters directlymodified and both AP slices can be pairs to a same updated core slice.

FIG. 7 illustrates example method 700 that facilitates adaptive pairingof an access point slice with a RAN slice and/or network core slice tosupport device handover, in accordance with aspects of the subjectdisclosure. Method 700, at 710, can comprise determining an access point(AP) slice based on device information of a device requesting connectionto an AP component. AP slicing can provide adaptable AP resourcesegmentation and granular service differentiation between devicesconnecting to an AP. Performance parameters of a connection to an APdevice can be reflected in a determined slice of AP device computingresources, e.g., one or more AP slices.

At 720, method 700 can comprise coordinating the AP slice with a networkcore component (CORE) slice, which can comprise communicatinginformation about the AP slice to a network core component to facilitatecoordination of an AP slice and one or more core slice, one or more RANslice, or combinations thereof. An AP slice can therefore select a coreslice that can meet the same requested performance parameters tostreamline moving data via the AP slice and the core slice. Inembodiments, information corresponding to the AP slice can becommunicated to a network core component that can attempt to provideaccess to, or determine, a coordinated core slice. In some embodiments,core slice information can be propagated to the AP device to facilitatecoordinated determination of an AP at 710, e.g., the determination ofthe AP slice can be based on predetermined core slice information. Insome embodiments, information about potential core slicing can becommunicated to the AP device, the AP device can determine the AP sliceat 710 in the context of the potential core slicing to enable thecoordination at 720 to already be possible, e.g., the AP device can beaware of the extents of core slicing so that the AP slice is within theextents and a coordinated core slice can be readily deployed. This canavoid conditions where the AP slice has performance parameters that arenot supported by any possible core slice(s), for example, a core slicemay have a predefined group of VNFs that can be limiting to some APslices, etc.

Method 700, at 730, can comprise determining a radio access network(RAN) slice in relation to the AP slice and the core slice. It is notedthat a UE can migrate, undergo a handover between, etc., an AP componentand a RAN component. Accordingly, method 700 can facilitate determininga RAN slice that can be coordinated with the AP slice of 710 and thecoordinated core slice of 720. In this regard, migrating a UE from an APto a RAN can be simplified and efficient. As an example, an AP-coreslice pair can support a first VNF. In this example, at 730, a RAN slicecan be determined that also supports the first VNF. Accordingly, where aUE employing the AP-core slice pair migrates away from an AP and into aRAN coverage area, the RAN slice with the first VNF can be employed.Where the example RAN slice supports the first VNF and the core slice ofthe AP-core slice pair also supports the first VNF, paring the RAN slicewith the core slice can also seamlessly support the first VNF that canbe in use by the migrating UE. As such, the example UE can be handedover from the AP to the RAN. In some embodiments, the UE can migratefrom a RAN to an AP in a similar manner as is disclosed elsewhereherein. In these embodiments, RAN slice information can be employed indetermining an AP slice that can then be inherently better coordinatedwith a core slice already associated with the RAN slice, which canfacilitate migrating a UE from the RAN to the AP device. This conceptwill be readily appreciated by those in the relevant arts, is consideredfully within the scope of the instant disclosure and is not discussed infurther detail here merely for the sake of clarity and brevity.

Method 700, at 740, can comprise migrating the device from the AP sliceof the AP component to the RAN slice of a RAN component, wherein the RANslice is coordinated with the core slice. At this point, method 700 canend. The determination of a RAN slice that is coordinated with the APslice, generally already comprised in an AP-core slice pair, can supportstreamlined migration of devices between an AP device and a RAN device.As such, a wireless device, such as a phone, cellular enabled tablet,laptop computer, etc., can switch from an AP component, e.g., a wirelesslocal area network (LAN), etc., to a RAN component, e.g., a wirelesswide area network (WAN), etc. This can be appreciated in an examplemoving a smartphone from a home wireless LAN network to a 5G cellularnetwork. In this regard, it can be less complex to already havesynchronized the performance of AP and RAN slices

FIG. 8 illustrates example method 800 enabling inferred adaptive pairingof an access point slice with a RAN slice and/or network core slice, inaccordance with aspects of the subject disclosure. Method 800, at 810,can comprise inferring an access point (AP) usage based on deviceinformation corresponding to a device requesting connection to an APcomponent. In some embodiments, an inference can be formed by a machinelearning component, an artificial intelligence component, etc., whichinference can be employed in determining, designating, sorting,ordering, ranking, etc., an AP, RAN, CN, or combination slice. Themachine learning component, the artificial intelligence component, etc.,can be generally referred to as an inference component. The inferencecomponent can generate an expected result based on models, patterns,historical data, etc. As such, an inference can be made based on deviceinformation as to AP usage. This AP usage can then be expected to defineperformance parameters for one or more AP slices.

Method 800, at 820, can comprise determining an AP slice based on theinferred AP usage. AP slicing can provide adaptable AP resourcesegmentation and granular service differentiation between devicesconnecting to an AP. The inferred AP usage from 810 can compriseinferred performance parameters for a connection to an AP device. As anexample, a user can regularly wake at 6 am for work and can spend sometime reviewing email early in the morning. Accordingly, in this example,it can be inferred that this behavior will occur tomorrow morning, suchthat an AP slice can be determined and ready for use the followingmorning, e.g., the inferred performance parameters can be reflected in aprecomputed AP slice.

At 830, method 800 can comprise coordinating the AP slice with a networkcore component (CORE) slice. Information about the AP slice can becommunicated to a network core component to facilitate coordination ofan AP slice and one or more core slice, one or more RAN slice, orcombinations thereof, as has been disclosed herein. It is noted thatwhere the AP slice is precomputed based on the inferences of 810, thecoordination with a core slice can also occur before the AP slice isactual employed, e.g., the coordination can be precoordinated based onthe inference and the corresponding predetermined AP slice. Aspreviously disclosed herein, for some embodiments, informationcorresponding to the AP slice can be communicated to a network corecomponent that can attempt to provide access to, or determine, acoordinated core slice. In some embodiments, core slice information canbe propagated to the AP device to facilitate coordinated determinationof an AP at 820, e.g., the determination of the AP slice can be based onpredetermined core slice information and the inferred AP usage. In someembodiments, information about potential core slicing can becommunicated to the AP device, the AP device can determine the AP sliceat 820 in the context of the inferred AP usage and the potential coreslicing to enable the coordination at 830 to already be possible, e.g.,the AP device can be aware of the extents of core slicing so that apredetermined AP slice is within the extents and a coordinated coreslice can be readily deployed. This can avoid conditions where thepredetermined AP slice has performance parameters that are not supportedby any possible core slice(s), e.g., the predetermined AP slice isoutside the extents of possible core slices.

At 840, method 800, in response to determining a change in device usage,can comprise updating the predetermined AP slice and the coordinationwith the core slice. At this point, method 800 can end. Adapting an APslice and the corresponding core slice can comprise responsivelyadapting the AP slice and coordinated core slice. However, in someembodiments, the adapting can be based on further inference from aninference component, e.g., an inference can be made that the demands onthe AP device will change, and an updated AP slice can again bepredetermined and precoordinated with a core slice, RAN slice, orcombination thereof, which can facilitate updating the AP slice at 840.In general, where the demands on the AP computing resources change, orupcoming change is inferred to be likely, the AP slice can be adapted.In this regard, adapting the AP slice, and also the core/RAN slice, cancomprise updating the slice parameters, VNFs, services, etc., adding aslice, deleting a slice, merging slices, dividing a slice(s),determining a new slice, etc.

FIG. 9 is a schematic block diagram of a computing environment 900 withwhich the disclosed subject matter can interact. The system 900comprises one or more remote component(s) 910. The remote component(s)910 can be hardware and/or software (e.g., threads, processes, computingdevices). In some embodiments, remote component(s) 910 can comprisenetwork core components 110-510, etc., RAN component 120, 320-520, etc.,AP component 120-520, etc., data store(s) 592, 992, 994, etc., UE 102,104, etc., or any other component that is located remotely from anothercomponent of systems 100-500, etc.

The system 900 also comprises one or more local component(s) 920. Thelocal component(s) 920 can be hardware and/or software (e.g., threads,processes, computing devices). In some embodiments, local component(s)920 can comprise network core components 110-510, etc., RAN component120, 320-520, etc., AP component 120-520, etc., data store(s) 592, 992,994, etc., UE 102, 104, etc., or any other component that is locatedlocal with another component of systems 100-500, etc.

One possible communication between a remote component(s) 910 and a localcomponent(s) 920 can be in the form of a data packet adapted to betransmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 910 and a local component(s)920 can be in the form of circuit-switched data adapted to betransmitted between two or more computer processes in radio time slots.The system 900 comprises a communication framework 990 that can beemployed to facilitate communications between the remote component(s)910 and the local component(s) 920, and can comprise an air interface,e.g., Uu interface of a UMTS network, via a long-term evolution (LTE)network, etc. Remote component(s) 910 can be operably connected to oneor more remote data store(s) 992, such as a hard drive, solid statedrive, SIM card, device memory, etc., that can be employed to storeinformation on the remote component(s) 910 side of communicationframework 990. Similarly, local component(s) 920 can be operablyconnected to one or more local data store(s) 994, that can be employedto store information on the local component(s) 920 side of communicationframework 990. As examples, AP slice information, RAN slice information,core slice information, etc., UE or other device information, e.g., 206,306, 506, etc., user preference information 508, etc., or otherinformation that can facilitate adaptive pairing of an access pointslice with a RAN slice and/or network core slice.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10 , and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules comprise routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can comprise both volatile and nonvolatilememory, by way of illustration, and not limitation, volatile memory 1020(see below), non-volatile memory 1022 (see below), disk storage 1024(see below), and memory storage 1046 (see below). Further, nonvolatilememory can be included in read only memory, programmable read onlymemory, electrically programmable read only memory, electricallyerasable read only memory, or flash memory. Volatile memory can compriserandom access memory, which acts as external cache memory. By way ofillustration and not limitation, random access memory is available inmany forms such as synchronous random-access memory, dynamicrandom-access memory, synchronous dynamic random-access memory, doubledata rate synchronous dynamic random-access memory, enhanced synchronousdynamic random-access memory, SynchLink dynamic random-access memory,and direct Rambus random access memory. Additionally, the disclosedmemory components of systems or methods herein are intended to comprise,without being limited to comprising, these and any other suitable typesof memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, comprising single-processoror multiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,netbook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, comprised innetwork core component 110-510, etc., RAN component 120, 320-520, etc.,AP component 120-520, etc., data store(s) 592, 992, 994, etc., UE 102,104, etc., or any other component that is located local with anothercomponent of systems 100-500, etc., can comprise a processing unit 1014,a system memory 1016, and a system bus 1018. System bus 1018 couplessystem components comprising, but not limited to, system memory 1016 toprocessing unit 1014. Processing unit 1014 can be any of variousavailable processors. Dual microprocessors and other multiprocessorarchitectures also can be employed as processing unit 1014.

System bus 1018 can be any of several types of bus structure(s)comprising a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures comprising, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 1194), and small computer systems interface.

System memory 1016 can comprise volatile memory 1020 and nonvolatilememory 1022. A basic input/output system, containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can compriseread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1020 comprises read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random-access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, SynchLink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1012 can also comprise removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 comprises, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can comprise storage media separately or in combination with otherstorage media comprising, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1024to system bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, read only memory, programmable readonly memory, electrically programmable read only memory, electricallyerasable read only memory, flash memory or other memory technology,compact disk read only memory, digital versatile disk or other opticaldisk storage, magnetic cassettes, magnetic tape, magnetic disk storageor other magnetic storage devices, or other tangible media which can beused to store desired information. In this regard, the term “tangible”herein as may be applied to storage, memory, or computer-readable media,is to be understood to exclude only propagating intangible signals perse as a modifier and does not relinquish coverage of all standardstorage, memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can comprisenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory, or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries, or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium. As such, for example, a computer-readable medium can compriseexecutable instructions stored thereon that, in response to execution,can cause a system comprising a processor to perform operationscomprising selecting an access point slice based on a device connectionparameter to an end point device. The operations can further comprisesynchronizing a network core slice with the access point slice and, inresponse to changes in the connection parameter between the end pointdevice and the access point device, adapting the access point slice andupdating the synchronization to the network core slice.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and comprises any informationdelivery or transport media. The term “modulated data signal” or signalsrefers to a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediacomprise wired media, such as a wired network or direct-wiredconnection, and wireless media such as acoustic, RF, infrared and otherwireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software comprises an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. In some embodiments, a user interface can allowentry of user preference information, etc., and can be embodied in atouch sensitive display panel, a mouse/pointer input to a graphical userinterface (GUI), a command line-controlled interface, etc., allowing auser to interact with computer 1012. Input devices 1036 comprise, butare not limited to, a pointing device such as a mouse, trackball,stylus, touch pad, keyboard, microphone, joystick, game pad, satellitedish, scanner, TV tuner card, digital camera, digital video camera, webcamera, cell phone, smartphone, tablet computer, etc. These and otherinput devices connect to processing unit 1014 through system bus 1018 byway of interface port(s) 1038. Interface port(s) 1038 comprise, forexample, a serial port, a parallel port, a game port, a universal serialbus, an infrared port, a Bluetooth port, an IP port, or a logical portassociated with a wireless service, etc. Output device(s) 1040 use someof the same type of ports as input device(s) 1036.

Thus, for example, a universal serial busport can be used to provideinput to computer 1012 and to output information from computer 1012 toan output device 1040. Output adapter 1042 is provided to illustratethat there are some output devices 1040 like monitors, speakers, andprinters, among other output devices 1040, which use special adapters.Output adapters 1042 comprise, by way of illustration and notlimitation, video and sound cards that provide means of connectionbetween output device 1040 and system bus 1018. It should be noted thatother devices and/or systems of devices provide both input and outputcapabilities such as remote computer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, a cloud service, code executing ina cloud-computing environment, a workstation, a microprocessor-basedappliance, a peer device, or other common network node and the like, andtypically comprises many or all of the elements described relative tocomputer 1012. A cloud computing environment, the cloud, or othersimilar terms can refer to computing that can share processing resourcesand data to one or more computer and/or other device(s) on an as neededbasis to enable access to a shared pool of configurable computingresources that can be provisioned and released readily. Cloud computingand storage solutions can store and/or process data in third-party datacenters which can leverage an economy of scale and can view accessingcomputing resources via a cloud service in a manner similar to asubscribing to an electric utility to access electrical energy, atelephone utility to access telephonic services, etc.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies comprise fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring, and the like. Widearea network technologies comprise, but are not limited to,point-to-point links, circuit-switching networks like integratedservices digital networks and variations thereon, packet switchingnetworks, and digital subscriber lines. As noted below, wirelesstechnologies may be used in addition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can comprise, for example, internaland external technologies such as modems, comprising regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, comprising what is described in the Abstract, is notintended to be exhaustive or to limit the disclosed embodiments to theprecise forms disclosed. While specific embodiments and examples aredescribed herein for illustrative purposes, various modifications arepossible that are considered within the scope of such embodiments andexamples, as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches, and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or a firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can comprise a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form. Moreover, the use of any particularembodiment or example in the present disclosure should not be treated asexclusive of any other particular embodiment or example, unlessexpressly indicated as such, e.g., a first embodiment that has aspect Aand a second embodiment that has aspect B does not preclude a thirdembodiment that has aspect A and aspect B. The use of granular examplesand embodiments is intended to simplify understanding of certainfeatures, aspects, etc., of the disclosed subject matter and is notintended to limit the disclosure to said granular instances of thedisclosed subject matter or to illustrate that combinations ofembodiments of the disclosed subject matter were not contemplated at thetime of actual or constructive reduction to practice.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “eNodeB,” “home Node B,” “home accesspoint,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream to and from a set ofsubscriber stations or provider enabled devices. Data and signalingstreams can comprise packetized or frame-based flows. Data or signalinformation exchange can comprise technology, such as, single user (SU)multiple-input and multiple-output (MIMO) (SU MIMO) radio(s), multipleuser (MU) MIMO (MU MIMO) radio(s), long-term evolution (LTE), LTEtime-division duplexing (TDD), global system for mobile communications(GSM), GSM EDGE Radio Access Network (GERAN), Wi Fi, WLAN, WiMax,CDMA2000, LTE new radio-access technology (LTE-NX), massive MIMOsystems, etc.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer toauthenticating a user-identity to a user-account. Authentication can, insome embodiments, refer to determining whether a user-identityrequesting a service from a telecom network is authorized to do sowithin the network or not. Call control and switching can referdeterminations related to the future course of a call stream acrosscarrier equipment based on the call signal processing. Charging can berelated to the collation and processing of charging data generated byvarious network nodes. Two common types of charging mechanisms found inpresent day networks can be prepaid charging and postpaid charging.Service invocation can occur based on some explicit action (e.g., calltransfer) or implicitly (e.g., call waiting). It is to be noted thatservice “execution” may or may not be a core network functionality asthird-party network/nodes may take part in actual service execution. Agateway can be present in the core network to access other networks.Gateway functionality can be dependent on the type of the interface withanother network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities, machine learning components, or automatedcomponents (e.g., supported through artificial intelligence, as througha capacity to make inferences based on complex mathematical formalisms),that can provide simulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks comprisebroadcast technologies (e.g., sub-Hertz, extremely low frequency, verylow frequency, low frequency, medium frequency, high frequency, veryhigh frequency, ultra-high frequency, super-high frequency, extremelyhigh frequency, terahertz broadcasts, etc.); Ethernet; X.25;powerline-type networking, e.g., Powerline audio video Ethernet, etc.;femtocell technology; Wi-Fi; worldwide interoperability for microwaveaccess; enhanced general packet radio service; second generationpartnership project (2G or 2GPP); third generation partnership project(3G or 3GPP); fourth generation partnership project (4G or 4GPP); longterm evolution (LTE); fifth generation partnership project (5G or 5GPP);sixth generation partnership project (6G or 6GPP); third generationpartnership project universal mobile telecommunications system; thirdgeneration partnership project 2; ultra mobile broadband; high speedpacket access; high speed downlink packet access; high speed uplinkpacket access; enhanced data rates for global system for mobilecommunication evolution radio access network; universal mobiletelecommunications system terrestrial radio access network; or long termevolution advanced. As an example, a millimeter wave broadcasttechnology can employ electromagnetic waves in the frequency spectrumfrom about 30 GHz to about 300 GHz. These millimeter waves can begenerally situated between microwaves (from about 1 GHz to about 30 GHz)and infrared (IR) waves, and are sometimes referred to extremely highfrequency (EHF). The wavelength (λ) for millimeter waves is typically inthe 1-mm to 10-mm range.

The term “infer”, or “inference” can generally refer to the process ofreasoning about, or inferring states of, the system, environment, user,and/or intent from a set of observations as captured via events and/ordata. Captured data and events can include user data, device data,environment data, data from sensors, sensor data, application data,implicit data, explicit data, etc. Inference, for example, can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events. Inference can also refer to techniquesemployed for composing higher-level events from a set of events and/ordata. Such inference results in the construction of new events oractions from a set of observed events and/or stored event data, whetherthe events, in some instances, can be correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources. Various classification schemes and/or systems(e.g., support vector machines, neural networks, expert systems,Bayesian belief networks, fuzzy logic, and data fusion engines) can beemployed in connection with performing automatic and/or inferred actionin connection with the disclosed subject matter.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices, and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A device, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: generatingan access point slice based on a device connection request; coordinatingthe access point slice with a network core slice; provisioning a slicepair based on the access point slice and the network core slice; and inresponse to a change in a performance parameter of the device connectionrequest, updating the access point slice and updating the coordinatingof the access point slice with the network core slice.
 2. The device ofclaim 1, wherein the device connection request indicates informationselected from a group of information comprising a device typeidentifier, a service identifier, an application identifier, a keyperformance metric threshold, a user identifier, and a locationidentifier.
 3. The device of claim 1, wherein the access point slicecorresponds to a portion of computing resources of a wireless local areanetwork component.
 4. The device of claim 3, wherein the wireless localarea network component employs an Institute of Electrical andElectronics Engineers 802.11 standard.
 5. The device of claim 1, whereincoordinating the access point slice with the network core slice resultsin the access point slice supporting a same virtual network function asis supported by the network core slice.
 6. The device of claim 1,wherein the operations further comprise coordinating the access pointslice with a radio access network slice.
 7. The device of claim 6,wherein coordinating the access point slice with the radio accessnetwork slice facilitates a handover operation that migrates a devicecorresponding to the device connection request from an access pointdevice corresponding to the access point slice to a radio access networkdevice corresponding to the radio access network slice.
 8. The device ofclaim 6, wherein coordinating the access point slice with the radioaccess network slice facilitates a handover operation that migrates adevice corresponding to the device connection request from a radioaccess network device corresponding to the radio access network slice toan access point device corresponding to the access point slice.
 9. Thedevice of claim 1, wherein generating the access point slice based onthe device connection request comprises inferring a usage of an accesspoint device corresponding to the access point slice.
 10. The device ofclaim 9, wherein inferring the usage anticipates receiving the deviceconnection request.
 11. The device of claim 10, wherein a result of theinferring is employed to predetermine a potential access point slicebased on anticipating, according to a threshold likelihood, receivingthe device connection request.
 12. A method, comprising: provisioning,by a system comprising a processor, an access point slice from computingresources of an access point device, wherein computing resourcesembodied via the access point slice are selected based on a connectionrequest of a user equipment; causing, by the system, provisioning of anetwork core slice that is coordinated with the access point slice; andupdating, by the system, the access point slice based on changes to aperformance of a connection between the user equipment and the accesspoint device.
 13. The method of claim 12, further comprising causing, bythe system, provisioning of a radio access network slice that iscoordinated with the access point slice to facilitate migrating the userequipment between a radio access network device and the access pointdevice.
 14. The method of claim 12, wherein provisioning the accesspoint slice comprises provisioning a virtual network function.
 15. Themethod of claim 12, wherein provisioning the access point slicecomprises provisioning radio spectrum corresponding to an Institute ofElectrical and Electronics Engineers 802.11 spectrum.
 16. The method ofclaim 12, wherein the provisioning comprised determining an inference ofcomputing resource usage by the access point device.
 17. Anon-transitory machine-readable storage medium, comprising executableinstructions that, when executed by a processor, facilitate performanceof operations, comprising: selecting an access point slice of an accesspoint device, wherein the access point slice is selected based on aconnection parameter corresponding to a connection between the accesspoint device and an end point device; synchronizing a network core slicewith the access point slice; and in response to changes in theconnection parameter between the end point device and the access pointdevice, adapting the access point slice and updating the synchronizingto the network core slice.
 18. The non-transitory machine-readablestorage medium of claim 17, wherein the operations further comprisesynchronizing a radio access network slice of a radio access networkdevice with the access point slice to facilitate migrating the end pointdevice between the radio access network device and the access pointdevice.
 19. The non-transitory machine-readable storage medium of claim17, wherein the access point device is comprised in a wireless localarea network.
 20. The non-transitory machine-readable storage medium ofclaim 19, wherein the network core slice corresponds to a wirelesspublic wide area network.